-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update plugin parent POM and plugin BOM #241
Conversation
9b7654e
to
3414f37
Compare
Thank you, @tszmytka! A release of this would facilitate Java 17 PCT testing. |
Gentle ping; a release of this would help me move forward with some draft PRs in |
I opened #243 |
Thanks @dblock! BTW if you implement automated plugin release then releasing a plugin becomes as simple as adding a special label when merging PRs. |
If you are suggesting that I contribute more to Jenkins, you must not have seen my GitHub profile. I have made my contribution to this plugin. What I need from the plugin maintainers is for that contribution to be released so that I can do plugin compatibility testing with it. |
@basil Thanks for your contributions. I am just saying that by the looks of that doc there's a bunch of things to change in this project. If you want to do it, it will get done faster. |
But if I propose a PR to implement automated plugin release, I risk that my time would be wasted because the maintainers do not want to use automated plugin release. The decision about whether or not to use automated plugin release belongs to the maintainers, not to me. Therefore, it makes sense for the same maintainers to implement automated plugin release. If the maintainer chooses not to implement automated plugin release, it is the maintainer's responsibility to do manual releases. |
I am a maintainer and can confirm that we want tag-based automated plugin release. |
Then I suggest you follow the instructions in Setting up automated plugin release , or (if you decline to follow those instructions) to perform a manual release. I will not do this work for you. It is the responsibility of the plugin maintainer, not contributors, to handle releases. |
@basil Thank you for your helpful suggestions. I will release this plugin sometime next month. |
But two months later? |
Well, I tried. Could use some help, #247 (comment) |
On July 24, I provided the help that was requested: #247 (comment) |
No description provided.